Feedback timing and uplink control information resource management for carrier aggregation activation

ABSTRACT

Aspects of the present disclose provide various methods and apparatuses for communicating, controlling, and configuring component carrier and bandwidth part (BWP). A scheduling entity receives a capability report from a user equipment (UE). The capability report indicates a capability of the UE to utilize at least one of carrier aggregation (CA) or one or more bandwidth parts. The scheduling entity transmits a command to the UE to reconfigure at least one of a CA configuration or a bandwidth part (BWP) configuration. The scheduling entity determines an anticipated response timing of an acknowledgment (ACK) of the command based on the capability report received from the UE. The scheduling entity receives the ACK according to the anticipated response timing.

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.16/124,116 filed Sep. 6, 2018, which claims the benefit of U.S.provisional patent application No. 62/557,016 filed Sep. 11, 2017, eachof which is incorporated herein by reference as if fully set forth belowin its entirety and for all applicable purposes.

TECHNICAL FIELD

The technology discussed below relates generally to wirelesscommunication systems and to carrier aggregation (CA) and bandwidth part(BWP) configuration and control in wireless communication.

INTRODUCTION

Carrier aggregation (CA) is a technique used in wireless communicationto increase the peak user data rates, improve connection reliability,and/or increase overall capacity of a network available to users. CA cancombine two or more component carriers that may be contiguous ornon-contiguous in frequency. In the next generation networks, one ormore bandwidth parts may be defined in a carrier band or componentcarrier (CC). A bandwidth part (BWP) is a contiguous set of physicalresource blocks within the carrier band. A user equipment may beconfigured to operate in a particular BWP that has a bandwidth narrowerthan the full bandwidth of the corresponding component carrier. As thedemand for mobile broadband access continues to increase, research anddevelopment continue to advance wireless communication technologiesrelated to CA and BWP not only to meet the growing demand for mobilebroadband access, but to advance and enhance the user experience withmobile communications.

BRIEF SUMMARY OF SOME EXAMPLES

The following presents a simplified summary of one or more aspects ofthe present disclosure, in order to provide a basic understanding ofsuch aspects. This summary is not an extensive overview of allcontemplated features of the disclosure, and is intended neither toidentify key or critical elements of all aspects of the disclosure norto delineate the scope of any or all aspects of the disclosure. Its solepurpose is to present some concepts of one or more aspects of thedisclosure in a simplified form as a prelude to the more detaileddescription that is presented later.

One aspect of the present disclosure provides a method of wirelesscommunication operable at a user equipment (UE). The UE transmits acapability report to a scheduling entity. The capability reportindicates a capability of the UE to transmit an acknowledgement (ACK) ofa command for reconfiguring at least one of a carrier aggregation (CA)configuration or a bandwidth part (BWP) configuration after apredetermined time delay in response to the command The UE receives thecommand from the scheduling entity. The UE transmits the ACK usinguplink resources scheduled by the scheduling entity according to anacknowledgment timeline selected based on the predetermined time delay.

Another aspect of the present disclosure provides a user equipment (UE)for wireless communication. The UE includes a communication interfaceconfigured to communicate with a scheduling entity, a memory, and aprocessor operatively coupled with the communication interface and thememory. The processor and the memory are configured to transmit acapability report to the scheduling entity. The capability reportindicates a capability of the UE to transmit an acknowledgement (ACK) ofa command for reconfiguring at least one of a carrier aggregation (CA)configuration or a bandwidth part configuration after a predeterminedtime delay in response to the command The processor and the memory arefurther configured to receive the command from the scheduling entity.The processor and the memory are further configured to transmit the ACKusing uplink resources scheduled by the scheduling entity according toan acknowledgment timeline selected based on the predetermined timedelay.

Another aspect of the present disclosure provides a user equipment (UE)for wireless communication. The UE includes means for transmitting acapability report to a scheduling entity. The capability reportindicates a capability of the UE to transmit an acknowledgement (ACK) ofa command for reconfiguring at least one of a carrier aggregation (CA)configuration or a bandwidth part (BWP) configuration after apredetermined time delay in response to the command The UE furtherincludes means for receiving the command from the scheduling entity. TheUE further includes means for transmitting the ACK using uplinkresources scheduled by the scheduling entity according to anacknowledgment timeline selected based on the predetermined time delay.

Another aspect of the present disclosure provides a non-transitorycomputer-readable medium stored with executable code for wirelesscommunication. The executable code includes instructions for causing auser equipment (UE) to transmit a capability report to a schedulingentity. The capability report indicates a capability of the UE totransmit an acknowledgement (ACK) of a command for reconfiguring atleast one of a carrier aggregation (CA) configuration or a bandwidthpart (BWP) configuration after a predetermined time delay in response tothe command The executable code further includes instructions forcausing the UE to receive the command from the scheduling entity. Theexecutable code further includes instructions for causing the UE totransmit the ACK using uplink resources scheduled by the schedulingentity according to an acknowledgment timeline selected based on thepredetermined delay.

These and other aspects of the invention will become more fullyunderstood upon a review of the detailed description, which follows.Other aspects, features, and embodiments of the present invention willbecome apparent to those of ordinary skill in the art, upon reviewingthe following description of specific, exemplary embodiments of thepresent invention in conjunction with the accompanying figures. Whilefeatures of the present invention may be discussed relative to certainembodiments and figures below, all embodiments of the present inventioncan include one or more of the advantageous features discussed herein.In other words, while one or more embodiments may be discussed as havingcertain advantageous features, one or more of such features may also beused in accordance with the various embodiments of the inventiondiscussed herein. In similar fashion, while exemplary embodiments may bediscussed below as device, system, or method embodiments it should beunderstood that such exemplary embodiments can be implemented in variousdevices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of a wireless communication system.

FIG. 2 is a conceptual illustration of an example of a radio accessnetwork.

FIG. 3 is a schematic illustration of an organization of wirelessresources in an air interface utilizing orthogonal frequency divisionalmultiplexing (OFDM).

FIG. 4 is a block diagram conceptually illustrating an example of ahardware implementation for a scheduling entity according to someaspects of the disclosure.

FIG. 5 is a block diagram conceptually illustrating an example of ahardware implementation for a scheduled entity according to some aspectsof the disclosure.

FIG. 6 is a diagram illustrating exemplary carrier aggregation signalingaccording to some aspects of the disclosure.

FIG. 7 is a diagram illustrating exemplary carrier aggregation (CA) andbandwidth part (BWP) configuration timing according to some aspects ofthe disclosure.

FIG. 8 is a diagram illustrating a BWP adaptation example according tosome aspects of the disclosure.

FIG. 9 is a diagram illustrating a second BWP adaptation exampleaccording to some aspects of the disclosure.

FIG. 10 is a diagram illustrating a third BWP adaptation exampleaccording to some aspects of the disclosure.

FIG. 11 is a flow chart illustrating an exemplary process forconfiguring CA or BWP according to some aspects of the presentdisclosure.

FIG. 12 is a flow chart illustrating another exemplary process forconfiguring CA or BWP according to some aspects of the presentdisclosure.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

While aspects and embodiments are described in this application byillustration to some examples, those skilled in the art will understandthat additional implementations and use cases may come about in manydifferent arrangements and scenarios. Innovations described herein maybe implemented across many differing platform types, devices, systems,shapes, sizes, packaging arrangements. For example, embodiments and/oruses may come about via integrated chip embodiments and othernon-module-component based devices (e.g., end-user devices, vehicles,communication devices, computing devices, industrial equipment,retail/purchasing devices, medical devices, AI-enabled devices, etc.).While some examples may or may not be specifically directed to use casesor applications, a wide assortment of applicability of describedinnovations may occur. Implementations may range a spectrum fromchip-level or modular components to non-modular, non-chip-levelimplementations and further to aggregate, distributed, or OEM devices orsystems incorporating one or more aspects of the described innovations.In some practical settings, devices incorporating described aspects andfeatures may also necessarily include additional components and featuresfor implementation and practice of claimed and described embodiments.For example, transmission and reception of wireless signals necessarilyincludes a number of components for analog and digital purposes (e.g.,hardware components including antenna, RF-chains, power amplifiers,modulators, buffer, processor(s), interleaver, adders/summers, etc.). Itis intended that innovations described herein may be practiced in a widevariety of devices, chip-level components, systems, distributedarrangements, end-user devices, etc. of varying sizes, shapes andconstitution.

Carrier aggregation (CA) is a technique widely used in wirelesscommunication to increase bandwidth, reliability, and/or throughput. Innext generation networks, for example 5G New Radio (NR), CA can beenhanced to provide more flexibility to handle user equipment (UE) withdiverse capabilities. In 5G NR, a bandwidth part (BWP) consists of agroup of contiguous physical resource blocks (PRBs), and each BWP mayhave its own numerology (e.g., cyclic prefix length and subcarrierspacing). One or multiple bandwidth part configurations for eachcomponent carrier (CC) may be configured for a UE. If BWP is used, a UEreceives and/or transmits within an active or configured BWP on acarrier. In some examples, a total bandwidth of a CC may be divided intomultiple BWPs (e.g., one to four BWPs per CC). The BWPs of a CC may havedifferent bandwidths like a narrowband BWP and a wideband BWP. In someexamples, the BWPs may overlap in frequency. Any change in theconfiguration (e.g., activation/deactivation) of component carriers andBWP(s) changes the data throughput available to the UE. Aspects of thepresent disclose provide various methods and apparatuses forcommunicating, controlling, and configuring CC and BWP.

The various concepts presented throughout this disclosure may beimplemented across a broad variety of telecommunication systems, networkarchitectures, and communication standards. Referring now to FIG. 1, asan illustrative example without limitation, various aspects of thepresent disclosure are illustrated with reference to a wirelesscommunication system 100. The wireless communication system 100 includesthree interacting domains: a core network 102, a radio access network(RAN) 104, and a user equipment (UE) 106. By virtue of the wirelesscommunication system 100, the UE 106 may be enabled to carry out datacommunication with an external data network 110, such as (but notlimited to) the Internet.

The RAN 104 may implement any suitable wireless communication technologyor technologies to provide radio access to the UE 106. As one example,the RAN 104 may operate according to 3^(rd) Generation PartnershipProject (3GPP) New Radio (NR) specifications, often referred to as 5G.As another example, the RAN 104 may operate under a hybrid of 5G NR andEvolved Universal Terrestrial Radio Access Network (eUTRAN) standards,often referred to as LTE. The 3GPP refers to this hybrid RAN as anext-generation RAN, or NG-RAN. Of course, many other examples may beutilized within the scope of the present disclosure.

As illustrated, the RAN 104 includes a plurality of base stations 108.Broadly, a base station is a network element in a radio access networkresponsible for radio transmission and reception in one or more cells toor from a UE. In different technologies, standards, or contexts, a basestation may variously be referred to by those skilled in the art as abase transceiver station (BTS), a radio base station, a radiotransceiver, a transceiver function, a basic service set (BSS), anextended service set (ESS), an access point (AP), a Node B (NB), aneNode B (eNB), a gNode B (gNB), or some other suitable terminology.

The radio access network 104 is further illustrated supporting wirelesscommunication for multiple mobile apparatuses. A mobile apparatus may bereferred to as user equipment (UE) in 3GPP standards, but may also bereferred to by those skilled in the art as a mobile station (MS), asubscriber station, a mobile unit, a subscriber unit, a wireless unit, aremote unit, a mobile device, a wireless device, a wirelesscommunications device, a remote device, a mobile subscriber station, anaccess terminal (AT), a mobile terminal, a wireless terminal, a remoteterminal, a handset, a terminal, a user agent, a mobile client, aclient, or some other suitable terminology. A UE may be an apparatusthat provides a user with access to network services.

Within the present document, a “mobile” apparatus need not necessarilyhave a capability to move, and may be stationary. The term mobileapparatus or mobile device broadly refers to a diverse array of devicesand technologies. UEs may include a number of hardware structuralcomponents sized, shaped, and arranged to help in communication; suchcomponents can include antennas, antenna arrays, RF chains, amplifiers,one or more processors, etc. electrically coupled to each other. Forexample, some non-limiting examples of a mobile apparatus include amobile, a cellular (cell) phone, a smart phone, a session initiationprotocol (SIP) phone, a laptop, a personal computer (PC), a notebook, anetbook, a smartbook, a tablet, a personal digital assistant (PDA), anda broad array of embedded systems, e.g., corresponding to an “Internetof things” (IoT). A mobile apparatus may additionally be an automotiveor other transportation vehicle, a remote sensor or actuator, a robot orrobotics device, a satellite radio, a global positioning system (GPS)device, an object tracking device, a drone, a multi-copter, aquad-copter, a remote control device, a consumer and/or wearable device,such as eyewear, a wearable camera, a virtual reality device, a smartwatch, a health or fitness tracker, a digital audio player (e.g., MP3player), a camera, a game console, etc. A mobile apparatus mayadditionally be a digital home or smart home device such as a homeaudio, video, and/or multimedia device, an appliance, a vending machine,intelligent lighting, a home security system, a smart meter, etc. Amobile apparatus may additionally be a smart energy device, a securitydevice, a solar panel or solar array, a municipal infrastructure devicecontrolling electric power (e.g., a smart grid), lighting, water, etc.;an industrial automation and enterprise device; a logistics controller;agricultural equipment; military defense equipment, vehicles, aircraft,ships, and weaponry, etc. Still further, a mobile apparatus may providefor connected medicine or telemedicine support, e.g., health care at adistance. Telehealth devices may include telehealth monitoring devicesand telehealth administration devices, whose communication may be givenpreferential treatment or prioritized access over other types ofinformation, e.g., in terms of prioritized access for transport ofcritical service data, and/or relevant QoS for transport of criticalservice data.

Wireless communication between a RAN 104 and a UE 106 may be describedas utilizing an air interface. Transmissions over the air interface froma base station (e.g., base station 108) to one or more UEs (e.g., UE106) may be referred to as downlink (DL) transmission. In accordancewith certain aspects of the present disclosure, the term downlink mayrefer to a point-to-multipoint transmission originating at a schedulingentity (described further below; e.g., base station 108). Another way todescribe this scheme may be to use the term broadcast channelmultiplexing. Transmissions from a UE (e.g., UE 106) to a base station(e.g., base station 108) may be referred to as uplink (UL)transmissions. In accordance with further aspects of the presentdisclosure, the term uplink may refer to a point-to-point transmissionoriginating at a scheduled entity (described further below; e.g., UE106).

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a base station 108) allocates resources forcommunication among some or all devices and equipment within its servicearea or cell. Within the present disclosure, as discussed further below,the scheduling entity may be responsible for scheduling, assigning,reconfiguring, and releasing resources for one or more scheduledentities. That is, for scheduled communication, UEs 106, which may bescheduled entities, may utilize resources allocated by the schedulingentity 108.

Base stations 108 are not the only entities that may function asscheduling entities. That is, in some examples, a UE may function as ascheduling entity, scheduling resources for one or more scheduledentities (e.g., one or more other UEs).

As illustrated in FIG. 1, a scheduling entity 108 may broadcast downlinktraffic 112 to one or more scheduled entities 106. Broadly, thescheduling entity 108 is a node or device responsible for schedulingtraffic in a wireless communication network, including the downlinktraffic 112 and, in some examples, uplink traffic 116 from one or morescheduled entities 106 to the scheduling entity 108. On the other hand,the scheduled entity 106 is a node or device that receives downlinkcontrol information 114, including but not limited to schedulinginformation (e.g., a grant), synchronization or timing information, orother control information from another entity in the wirelesscommunication network such as the scheduling entity 108. The schedulingentities 108 may communicate with the scheduled entities 106 usingcarrier aggregation and bandwidth parts.

In general, base stations 108 may include a backhaul interface forcommunication with a backhaul portion 120 of the wireless communicationsystem. The backhaul 120 may provide a link between a base station 108and the core network 102. Further, in some examples, a backhaul networkmay provide interconnection between the respective base stations 108.Various types of backhaul interfaces may be employed, such as a directphysical connection, a virtual network, or the like using any suitabletransport network.

The core network 102 may be a part of the wireless communication system100, and may be independent of the radio access technology used in theRAN 104. In some examples, the core network 102 may be configuredaccording to 5G standards (e.g., 5GC). In other examples, the corenetwork 102 may be configured according to a 4G evolved packet core(EPC), or any other suitable standard or configuration.

Referring now to FIG. 2, by way of example and without limitation, aschematic illustration of a RAN 200 is provided. In some examples, theRAN 200 may be the same as the RAN 104 described above and illustratedin FIG. 1. The geographic area covered by the RAN 200 may be dividedinto cellular regions (cells) that can be uniquely identified by a userequipment (UE) based on an identification broadcasted from one accesspoint or base station. FIG. 2 illustrates macrocells 202, 204, and 206,and a small cell 208, each of which may include one or more sectors (notshown). A sector is a sub-area of a cell. All sectors within one cellare served by the same base station. A radio link within a sector can beidentified by a single logical identification belonging to that sector.In a cell that is divided into sectors, the multiple sectors within acell can be formed by groups of antennas with each antenna responsiblefor communication with UEs in a portion of the cell.

In FIG. 2, two base stations 210 and 212 are shown in cells 202 and 204;and a third base station 214 is shown controlling a remote radio head(RRH) 216 in cell 206. That is, a base station can have an integratedantenna or can be connected to an antenna or RRH by feeder cables. Inthe illustrated example, the cells 202, 204, and 126 may be referred toas macrocells, as the base stations 210, 212, and 214 support cellshaving a large size. Further, a base station 218 is shown in the smallcell 208 (e.g., a microcell, picocell, femtocell, home base station,home Node B, home eNode B, etc.) which may overlap with one or moremacrocells. In this example, the cell 208 may be referred to as a smallcell, as the base station 218 supports a cell having a relatively smallsize. Cell sizing can be done according to system design as well ascomponent constraints.

It is to be understood that the radio access network 200 may include anynumber of wireless base stations and cells. Further, a relay node may bedeployed to extend the size or coverage area of a given cell. The basestations 210, 212, 214, 218 provide wireless access points to a corenetwork for any number of mobile apparatuses. In some examples, the basestations 210, 212, 214, and/or 218 may be the same as the basestation/scheduling entity 108 described above and illustrated in FIG. 1.

FIG. 2 further includes a quadcopter or drone 220, which may beconfigured to function as a base station. That is, in some examples, acell may not necessarily be stationary, and the geographic area of thecell may move according to the location of a mobile base station such asthe quadcopter 220.

Within the RAN 200, the cells may include UEs that may be incommunication with one or more sectors of each cell. Further, each basestation 210, 212, 214, 218, and 220 may be configured to provide anaccess point to a core network 102 (see FIG. 1) for all the UEs in therespective cells. For example, UEs 222 and 224 may be in communicationwith base station 210; UEs 226 and 228 may be in communication with basestation 212; UEs 230 and 232 may be in communication with base station214 by way of RRH 216; UE 234 may be in communication with base station218; and UE 236 may be in communication with mobile base station 220. Insome examples, the UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240,and/or 242 may be the same as the UE/scheduled entity 106 describedabove and illustrated in FIG. 1. A UE 230 may communicate with a basestation 216 using one or more component carriers (CCs), and each CC mayprovide one or more bandwidth parts (BWPs).

In some examples, a mobile network node (e.g., quadcopter 220) may beconfigured to function as a UE. For example, the quadcopter 220 mayoperate within cell 202 by communicating with base station 210.

In a further aspect of the RAN 200, sidelink signals may be used betweenUEs without necessarily relying on scheduling or control informationfrom a base station. For example, two or more UEs (e.g., UEs 226 and228) may communicate with each other using peer to peer (P2P) orsidelink signals 227 without relaying that communication through a basestation (e.g., base station 212). In a further example, UE 238 isillustrated communicating with UEs 240 and 242. Here, the UE 238 mayfunction as a scheduling entity or a primary sidelink device, and UEs240 and 242 may function as a scheduled entity or a non-primary (e.g.,secondary) sidelink device. In still another example, a UE may functionas a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P),or vehicle-to-vehicle (V2V) network, and/or in a mesh network. In a meshnetwork example, UEs 240 and 242 may optionally communicate directlywith one another in addition to communicating with the scheduling entity238. Thus, in a wireless communication system with scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, or a mesh configuration, a scheduling entity and one ormore scheduled entities may communicate utilizing the scheduledresources.

In the radio access network 200, the ability for a UE to communicatewhile moving, independent of its location, is referred to as mobility.The various physical channels between the UE and the radio accessnetwork are generally set up, maintained, and released under the controlof an access and mobility management function (AMF, not illustrated,part of the core network 102 in FIG. 1), which may include a securitycontext management function (SCMF) that manages the security context forboth the control plane and the user plane functionality, and a securityanchor function (SEAF) that performs authentication.

In various aspects of the disclosure, a radio access network 200 mayutilize DL-based mobility or UL-based mobility to enable mobility andhandovers (i.e., the transfer of a UE's connection from one radiochannel to another). In a network configured for DL-based mobility,during a call with a scheduling entity, or at any other time, a UE maymonitor various parameters of the signal from its serving cell as wellas various parameters of neighboring cells. Depending on the quality ofthese parameters, the UE may maintain communication with one or more ofthe neighboring cells. During this time, if the UE moves from one cellto another, or if signal quality from a neighboring cell exceeds thatfrom the serving cell for a given amount of time, the UE may undertake ahandoff or handover from the serving cell to the neighboring (target)cell. For example, UE 224 (illustrated as a vehicle, although anysuitable form of UE may be used) may move from the geographic areacorresponding to its serving cell 202 to the geographic areacorresponding to a neighbor cell 206. When the signal strength orquality from the neighbor cell 206 exceeds that of its serving cell 202for a given amount of time, the UE 224 may transmit a reporting messageto its serving base station 210 indicating this condition. In response,the UE 224 may receive a handover command, and the UE may undergo ahandover to the cell 206.

In a network configured for UL-based mobility, UL reference signals fromeach

UE may be utilized by the network to select a serving cell for each UE.In some examples, the base stations 210, 212, and 214/216 may broadcastunified synchronization signals (e.g., unified Primary SynchronizationSignals (PSSs), unified Secondary Synchronization Signals (SSSs) andunified Physical Broadcast Channels (PBCH)). The UEs 222, 224, 226, 228,230, and 232 may receive the unified synchronization signals, derive thecarrier frequency and slot timing from the synchronization signals, andin response to deriving timing, transmit an uplink pilot or referencesignal. The uplink pilot signal transmitted by a UE (e.g., UE 224) maybe concurrently received by two or more cells (e.g., base stations 210and 214/216) within the radio access network 200. Each of the cells maymeasure a strength of the pilot signal, and the radio access network(e.g., one or more of the base stations 210 and 214/216 and/or a centralnode within the core network) may determine a serving cell for the UE224. As the UE 224 moves through the radio access network 200, thenetwork may continue to monitor the uplink pilot signal transmitted bythe UE 224. When the signal strength or quality of the pilot signalmeasured by a neighboring cell exceeds that of the signal strength orquality measured by the serving cell, the network 200 may handover theUE 224 from the serving cell to the neighboring cell, with or withoutinforming the UE 224.

Although the synchronization signal transmitted by the base stations210, 212, and 214/216 may be unified, the synchronization signal may notidentify a particular cell, but rather may identify a zone of multiplecells operating on the same frequency and/or with the same timing. Theuse of zones in 5G networks or other next generation communicationnetworks enables the uplink-based mobility framework and improves theefficiency of both the UE and the network, since the number of mobilitymessages that need to be exchanged between the UE and the network may bereduced.

In various implementations, the air interface in the radio accessnetwork 200 may utilize licensed spectrum, unlicensed spectrum, orshared spectrum. Licensed spectrum provides for exclusive use of aportion of the spectrum, generally by virtue of a mobile networkoperator purchasing a license from a government regulatory body.Unlicensed spectrum provides for shared use of a portion of the spectrumwithout need for a government-granted license. While compliance withsome technical rules is generally still required to access unlicensedspectrum, generally, any operator or device may gain access. Sharedspectrum may fall between licensed and unlicensed spectrum, whereintechnical rules or limitations may be required to access the spectrum,but the spectrum may still be shared by multiple operators and/ormultiple RATs. For example, the holder of a license for a portion oflicensed spectrum may provide licensed shared access (LSA) to share thatspectrum with other parties, e.g., with suitable licensee-determinedconditions to gain access.

The air interface in the radio access network 200 may utilize one ormore duplexing algorithms Duplex refers to a point-to-pointcommunication link where both endpoints can communicate with one anotherin both directions. Full duplex means both endpoints can simultaneouslycommunicate with one another. Half duplex means only one endpoint cansend information to the other at a time. In a wireless link, a fullduplex channel generally relies on physical isolation of a transmitterand receiver, and suitable interference cancellation technologies. Fullduplex emulation is frequently implemented for wireless links byutilizing frequency division duplex (FDD) or time division duplex (TDD).In FDD, transmissions in different directions operate at differentcarrier frequencies. In TDD, transmissions in different directions on agiven channel are separated from one another using time divisionmultiplexing. That is, at some times the channel is dedicated fortransmissions in one direction, while at other times the channel isdedicated for transmissions in the other direction, where the directionmay change very rapidly, e.g., several times per slot.

In order for transmissions over the radio access network 200 to obtain alow block error rate (BLER) while still achieving very high data rates,channel coding may be used. That is, wireless communication maygenerally utilize a suitable error correcting block code. In a typicalblock code, an information message or sequence is split up into codeblocks (CBs), and an encoder (e.g., a CODEC) at the transmitting devicethen mathematically adds redundancy to the information message.Exploitation of this redundancy in the encoded information message canimprove the reliability of the message, enabling correction for any biterrors that may occur due to the noise.

In early 5G NR specifications, user data is coded using quasi-cycliclow-density parity check (LDPC) with two different base graphs: one basegraph is used for large code blocks and/or high code rates, while theother base graph is used otherwise. Control information and the physicalbroadcast channel (PBCH) are coded using Polar coding, based on nestedsequences. For these channels, puncturing, shortening, and repetitionare used for rate matching.

However, those of ordinary skill in the art will understand that aspectsof the present disclosure may be implemented utilizing any suitablechannel code. Various implementations of scheduling entities 108 andscheduled entities 106 may include suitable hardware and capabilities(e.g., an encoder, a decoder, and/or a CODEC) to utilize one or more ofthese channel codes for wireless communication.

The air interface in the radio access network 200 may utilize one ormore multiplexing and multiple access algorithms to enable simultaneouscommunication of the various devices. For example, 5G NR specificationsprovide multiple access for UL transmissions from UEs 222 and 224 tobase station 210, and for multiplexing for DL transmissions from basestation 210 to one or more UEs 222 and 224, utilizing orthogonalfrequency division multiplexing (OFDM) with a cyclic prefix (CP). Inaddition, for UL transmissions, 5G NR specifications provide support fordiscrete Fourier transform-spread-OFDM (DFT-s-OFDM) with a CP (alsoreferred to as single-carrier FDMA (SC-FDMA)). However, within the scopeof the present disclosure, multiplexing and multiple access are notlimited to the above schemes, and may be provided utilizing timedivision multiple access (TDMA), code division multiple access (CDMA),frequency division multiple access (FDMA), sparse code multiple access(SCMA), resource spread multiple access (RSMA), or other suitablemultiple access schemes. Further, multiplexing DL transmissions from thebase station 210 to UEs 222 and 224 may be provided utilizing timedivision multiplexing (TDM), code division multiplexing (CDM), frequencydivision multiplexing (FDM), orthogonal frequency division multiplexing(OFDM), sparse code multiplexing (SCM), or other suitable multiplexingschemes.

Various aspects of the present disclosure will be described withreference to an OFDM waveform, schematically illustrated in FIG. 3. Itshould be understood by those of ordinary skill in the art that thevarious aspects of the present disclosure may be applied to aDFT-s-OFDMA waveform in substantially the same way as described hereinbelow. That is, while some examples of the present disclosure may focuson an OFDM link for clarity, it should be understood that the sameprinciples may be applied as well to DFT-s-OFDMA waveforms.

Within the present disclosure, a frame refers to a predeterminedduration (e.g., 10 ms) for wireless transmissions, with each frameconsisting of a predetermined number (e.g., 10) of subframes of, forexample, 1 ms each. On a given carrier, there may be one set of framesin the UL, and another set of frames in the DL. Referring now to FIG. 3,an expanded view of an exemplary DL subframe 302 is illustrated, showingan OFDM resource grid 304. However, as those skilled in the art willreadily appreciate, the PHY transmission structure for any particularapplication may vary from the example described here, depending on anynumber of factors. Here, time is in the horizontal direction with unitsof OFDM symbols; and frequency is in the vertical direction with unitsof subcarriers or tones.

The resource grid 304 is divided into multiple resource elements (REs)306. An RE, which is 1 subcarrier×1 symbol, is the smallest discretepart of the time-frequency grid, and contains a single complex valuerepresenting data from a physical channel or signal. Depending on themodulation utilized in a particular implementation, each RE mayrepresent one or more bits of information. In some examples, a block ofREs may be referred to as a physical resource block (PRB) or more simplya resource block (RB) 308, which contains any suitable number ofconsecutive subcarriers in the frequency domain. In one example, an RBmay include 12 subcarriers, a number independent of the numerology used.In some examples, depending on the numerology, an RB may include anysuitable number of consecutive OFDM symbols in the time domain. Withinthe present disclosure, it is assumed that a single RB such as the RB308 entirely corresponds to a single direction of communication (eithertransmission or reception for a given device).

A UE generally utilizes only a subset of the resource grid 304. An RBmay be the smallest unit of resources that can be allocated to a UE.Thus, the more RBs scheduled for a UE, and the higher the modulationscheme chosen for the air interface, the higher the data rate for theUE. For example, a CC corresponds to a certain number of RBs that may beorganized or configured into different BWPs that may or may not overlapin frequency.

In this illustration, the RB 308 is shown as occupying less than theentire bandwidth of the subframe 302, with some subcarriers illustratedabove and below the RB 308. In a given implementation, the subframe 302may have a bandwidth corresponding to any number of one or more RBs 308.Further, in this illustration, the RB 308 is shown as occupying lessthan the entire duration of the subframe 302, although this is merelyone possible example.

Each 1 ms subframe 302 may consist of one or multiple adjacent slots. Inthe example shown in FIG. 3, one subframe 302 includes four slots 310,as an illustrative example. In some examples, a slot may be definedaccording to a specified number of OFDM symbols with a given cyclicprefix (CP) length. For example, a slot may include 7 or 14 OFDM symbolswith a nominal CP. Additional examples may include mini-slots having ashorter duration (e.g., one or two OFDM symbols). These mini-slots mayin some cases be transmitted occupying resources scheduled for ongoingslot transmissions for the same or for different UEs.

An expanded view of one of the slots 310 illustrates the slot 310including a control region 312 and a data region 314. In general, thecontrol region 312 may carry control channels (e.g., PDCCH), and thedata region 314 may carry data channels (e.g., PDSCH or PUSCH). Ofcourse, a slot may contain all DL, all UL, or at least one DL portionand at least one UL portion. The simple structure illustrated in FIG. 3is merely exemplary in nature, and different slot structures may beutilized, and may include one or more of each of the control region(s)and data region(s).

Although not illustrated in FIG. 3, the various REs 306 within an RB 308may be scheduled to carry one or more physical channels, includingcontrol channels, shared channels, data channels, etc. Other REs 306within the RB 308 may also carry pilots or reference signals, includingbut not limited to a demodulation reference signal (DMRS) a controlreference signal (CRS), or a sounding reference signal (SRS). Thesepilots or reference signals may provide for a receiving device toperform channel estimation of the corresponding channel, which mayenable coherent demodulation/detection of the control and/or datachannels within the RB 308.

In a DL transmission, the transmitting device (e.g., the schedulingentity 108) may allocate one or more REs 306 (e.g., within a controlregion 312) to carry DL control information 114 including one or more DLchannels, such as a PBCH; a PSS; a SSS; a physical control formatindicator channel (PCFICH); a physical hybrid automatic repeat request(HARQ) indicator channel (PHICH); and/or a physical downlink controlchannel (PDCCH), etc., to one or more scheduled entities 106. The PCFICHprovides information to assist a receiving device in receiving anddecoding the PDCCH. The PDCCH carries downlink control information (DCI)including but not limited to power control commands, schedulinginformation, a grant, and/or an assignment of REs for DL and ULtransmissions. The PHICH carries HARQ feedback transmissions such as anacknowledgment (ACK) or negative acknowledgment (NACK). HARQ is atechnique well-known to those of ordinary skill in the art, wherein theintegrity of packet transmissions may be checked at the receiving sidefor accuracy, e.g., utilizing any suitable integrity checking mechanism,such as a checksum or a cyclic redundancy check (CRC). If the integrityof the transmission is confirmed, an ACK may be transmitted, whereas ifnot confirmed, a NACK may be transmitted. In response to a NACK, thetransmitting device may send a HARQ retransmission, which may implementchase combining, incremental redundancy, etc.

In an UL transmission, the transmitting device (e.g., the scheduledentity 106) may utilize one or more REs 306 to carry UL controlinformation 118 including one or more UL control channels, such as aphysical uplink control channel (PUCCH), to the scheduling entity 108.UL control information may include a variety of packet types andcategories, including pilots, reference signals, and informationconfigured to enable or assist in decoding uplink data transmissions. Insome examples, the control information 118 may include a schedulingrequest (SR), e.g., a request for the scheduling entity 108 to scheduleuplink transmissions. Here, in response to the SR transmitted on thecontrol channel 118, the scheduling entity 108 may transmit downlinkcontrol information 114 that may schedule resources for uplink packettransmissions. UL control information may also include HARQ feedback,channel state feedback (CSF), or any other suitable UL controlinformation.

In addition to control information, one or more REs 306 (e.g., withinthe data region 314) may be allocated for user data or traffic data.Such traffic may be carried on one or more traffic channels, such as,for a DL transmission, a physical downlink shared channel (PDSCH); orfor an UL transmission, a physical uplink shared channel (PUSCH). Insome examples, one or more REs 306 within the data region 314 may beconfigured to carry system information blocks (SIBs), carryinginformation that may enable access to a given cell.

The channels or carriers described above and illustrated in FIGS. 1 and3 are not necessarily all the channels or carriers that may be utilizedbetween a scheduling entity 108 and scheduled entities 106, and those ofordinary skill in the art will recognize that other channels or carriersmay be utilized in addition to those illustrated, such as other traffic,control, and feedback channels.

These physical channels described above are generally multiplexed andmapped to transport channels for handling at the medium access control(MAC) layer. Transport channels carry blocks of information calledtransport blocks (TB). The transport block size (TBS), which maycorrespond to a number of bits of information, may be a controlledparameter, based on the modulation and coding scheme (MCS) and thenumber of RBs in a given transmission.

FIG. 4 is a block diagram illustrating an example of a hardwareimplementation for a scheduling entity 400 employing a processing system414. For example, the scheduling entity 400 may be a user equipment (UE)as illustrated in any one or more of FIGS. 1, 2, and/or 6. In anotherexample, the scheduling entity 400 may be a base station as illustratedin any one or more of FIGS. 1, 2, and/or 6.

The scheduling entity 400 may be implemented with a processing system414 that includes one or more processors 404. Examples of processors 404include microprocessors, microcontrollers, digital signal processors(DSPs), field programmable gate arrays (FPGAs), programmable logicdevices (PLDs), state machines, gated logic, discrete hardware circuits,and other suitable hardware configured to perform the variousfunctionality described throughout this disclosure. In various examples,the scheduling entity 400 may be configured to perform any one or moreof the functions described herein. That is, the processor 404, asutilized in a scheduling entity 400, may be used to implement any one ormore of the processes and procedures described and illustrated in FIGS.6-12.

In this example, the processing system 414 may be implemented with a busarchitecture, represented generally by the bus 402. The bus 402 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 414 and the overall designconstraints. The bus 402 communicatively couples together variouscircuits including one or more processors (represented generally by theprocessor 404), a memory 405, and computer-readable media (representedgenerally by the computer-readable medium 406). The memory 405 may storea capability report that indicates UE category and various otherinformation, for example, the CA and BWP capability, of the scheduledentity 500 (e.g., UE). The bus 402 may also link various other circuitssuch as timing sources, peripherals, voltage regulators, and powermanagement circuits, which are well known in the art, and therefore,will not be described any further. A bus interface 408 provides aninterface between the bus 402 and a transceiver 410. The transceiver 410provides a communication interface or means for communicating withvarious other apparatus over a transmission medium. Depending upon thenature of the apparatus, a user interface 412 (e.g., keypad, display,speaker, microphone, joystick) may also be provided. Of course, such auser interface 412 is optional, and may be omitted in some examples,such as a base station.

In some aspects of the disclosure, the processor 404 may includecircuitry configured for various functions, including, for example, aprocessing circuit 440 and a communication circuit 442. For example, thecircuitry may be configured to implement one or more of the functionsdescribed below in relation to FIGS. 6-12. The processing circuit 440may be configured to perform various data processing functions tofacilitate communication using the wireless communication circuit 442.The communication circuit 442 may be configured to perform variouswireless communication functions including, encoding, decoding,multiplexing, demultiplexing, interleaving, deinterleaving, noisecancellation, channel estimation, channel coding, carrier aggregation,bandwidth part adaptation, etc. In some examples, the scheduling entitymay receive a UE capability report that may be stored in the memory 405.

The processor 404 is responsible for managing the bus 402 and generalprocessing, including the execution of software stored on thecomputer-readable medium 406. The software, when executed by theprocessor 404, causes the processing system 414 to perform the variousfunctions described below for any particular apparatus. Thecomputer-readable medium 406 and the memory 405 may also be used forstoring data that is manipulated by the processor 404 when executingsoftware.

One or more processors 404 in the processing system may executesoftware. Software shall be construed broadly to mean instructions,instruction sets, code, code segments, program code, programs,subprograms, software modules, applications, software applications,software packages, routines, subroutines, objects, executables, threadsof execution, procedures, functions, etc., whether referred to assoftware, firmware, middleware, microcode, hardware descriptionlanguage, or otherwise. The software may reside on a computer-readablemedium 406. The computer-readable medium 406 may be a non-transitorycomputer-readable medium. A non-transitory computer-readable mediumincludes, by way of example, a magnetic storage device (e.g., hard disk,floppy disk, magnetic strip), an optical disk (e.g., a compact disc (CD)or a digital versatile disc (DVD)), a smart card, a flash memory device(e.g., a card, a stick, or a key drive), a random access memory (RAM), aread only memory (ROM), a programmable ROM (PROM), an erasable PROM(EPROM), an electrically erasable PROM (EEPROM), a register, a removabledisk, and any other suitable medium for storing software and/orinstructions that may be accessed and read by a computer. Thecomputer-readable medium 406 may reside in the processing system 414,external to the processing system 414, or distributed across multipleentities including the processing system 414. The computer-readablemedium 406 may be embodied in a computer program product. By way ofexample, a computer program product may include a computer-readablemedium in packaging materials. Those skilled in the art will recognizehow best to implement the described functionality presented throughoutthis disclosure depending on the particular application and the overalldesign constraints imposed on the overall system.

In one or more examples, the computer-readable storage medium 406 mayinclude software configured for various functions, including, forexample, processing instructions 452 and communication instructions 454.For example, the software may be configured to implement one or more ofthe functions described in relation to FIGS. 6-12.

FIG. 5 is a conceptual diagram illustrating an example of a hardwareimplementation for an exemplary scheduled entity 500 employing aprocessing system 514. In accordance with various aspects of thedisclosure, an element, or any portion of an element, or any combinationof elements may be implemented with a processing system 514 thatincludes one or more processors 504. For example, the scheduled entity500 may be a user equipment (UE) as illustrated in any one or more ofFIGS. 1, 2, and/or 6.

The processing system 514 may be substantially the same as theprocessing system 414 illustrated in FIG. 4, including a bus interface508, a bus 502, memory 505, a processor 504, and a computer-readablemedium 506. The memory 505 may store a capability report that indicatesUE category and various other information, for example, the CA and BWPcapability, of the scheduled entity 500. Furthermore, the scheduledentity 500 may include a user interface 512 and a transceiver 510substantially similar to those described above in FIG. 4. The scheduledentity 50 may transmit the UE capability report to a scheduling entity400. That is, the processor 504, as utilized in a scheduled entity 500,may be used to implement any one or more of the processes described andillustrated in FIGS. 6-12.

In some aspects of the disclosure, the processor 504 may includecircuitry configured for various functions, including, for example, aprocessing circuit 540 and a communication circuit 542. For example, thecircuitry may be configured to implement one or more of the functionsdescribed in relation to FIGS. 6-12. The processing instructions 540 maybe configured to perform various data processing functions to facilitatecommunication using the wireless communication circuit 542. Thecommunication circuit 542 may be configured to perform various wirelesscommunication functions including, encoding, decoding, multiplexing,demultiplexing, interleaving, deinterleaving, noise cancellation,channel estimation, channel coding, carrier aggregation, bandwidth partadaptation, etc. In one or more examples, the computer-readable storagemedium 506 may include software configured for various functions,including, for example, processing instructions 552 and communicationinstructions 554. For example, the software may be configured toimplement one or more of the functions described in relation to FIGS.6-12.

FIG. 6 is a diagram illustrating exemplary carrier aggregation signaling600 according to some aspects of the disclosure. A UE 602 may obtaincommunication services from a base station (BS) 604 by performing anaccess procedure 606. One example of the access procedure 606 may be arandom access procedure (RACH) or the like. In one aspect of thedisclosure, the UE 602 may be any of the UEs illustrated in FIGS. 1, 2,and/or 5, for example, scheduled entity 500 of FIG. 5. In one aspect ofthe disclosure, the BS 604 may be any of the base stations illustratedin FIGS. 1, 2, and/or 4, for example, scheduling entity 400 of FIG. 4.

After completing the access procedure 606, the UE may receive a UEcapability enquiry message 608 from the BS 604. The BS 604 uses the UEcapability enquiry message to specify which information it wants to getfrom the UE. Then, the UE 602 reports its capability informationrequested by the BS 604. For example, the UE 602 may send UE capabilityinformation 610 to report its capability and/or UE category. The UEcapability information 610 may include UE category, supported carrieraggregation configuration(s), supported bandwidth part configuration(s),supported RAT(s), etc. In one example, the UE capability information 610may indicate UE acknowledgment timing in response to carrier aggregation(CA) and bandwidth part (BWP) configuration commands The BS 604 may senda connection reconfiguration message 612 to the UE 602 to change certainconfiguration of the connection or communication between the UE 602 andthe BS 604. In one example, the connection reconfiguration message 612may include a CA configuration command and/or a BWP configurationcommand A CA configuration command may activate or deactivate the use ofCA at the UE 602. The CA configuration command may indicate the CC(s) tobe activated and/or deactivated. A BWP command may activate, deactivate,or switch BWP(s). In response to the connection reconfiguration message612, the UE 602 may transmit an acknowledgment message (e.g., CA/BWP ACK614). For example, the CA/BWP ACK 614 may indicate that the UE receivedthe CA or BWP command After a certain time period, the UE 602 completesthe reconfiguration processes to reconfigure (e.g., activate,deactivate, or switch) CA and/or BWP. Then the UE 602 may transmit areconfiguration complete message 616 to inform the BS 604 that thereconfiguration of CA and/or BWP has been completed.

FIG. 7 is a diagram illustrating exemplary CA and BWP configurationtiming according to some aspects of the disclosure. In one aspect of thedisclosure, the BS 604 may transmit a CA configuration command or BWPconfiguration command using DCI carried in a PDCCH 702. In response tothe CA/BWP configuration command (e.g., connection reconfigurationmessage 612), the UE 602 may transmit an acknowledgment message (e.g.,CA/BWP ACK 614 in FIG. 6), for example, in a PUCCH 704. The ACK responsetiming 706 between the DCI activation of CA/BWP configuration commandand ACK transmission may depend on UE capability or category. In someexamples, the base station 604 may determine the ACK timing based on thereported UE capability category. That is, different UEs may havedifferent ACK response timing 706. For example, a UE with betterprocessing power and/or communication capability may be able to transmitthe ACK in a PUCCH 704 faster than another UE with inferior processingpower and/or communication capability.

In one aspect of the disclosure, the BS 604 may transmit a CAconfiguration command or BWP configuration command using a MAC controlelement (CE) that may be carried in a PDSCH 708. In response to theCA/BWP configuration command (e.g., connection reconfiguration message612), the UE 602 may transmit an acknowledgment message (e.g., CA/BWPACK 614 in FIG. 6), for example, in a PUCCH 704. The ACK timing 710between the MAC CE activation and ACK transmission may depend on UEcapability or category. That is, different UEs may have different ACKresponse timing 710 in response to a CA/BWP configuration commandcarried in a MAC CE. After transmitting the ACK, the UE needs certaintime to reconfigure its software and/or hardware to operate in the newCA/BWP configuration. For example, the UE may need to activate ordeactivate CCs, and/or activate/deactivate/swap BWP(s). In someexamples, the timeline 712 of the DCI-based CA/BWPconfiguration/reconfiguration may be different (e.g., longer or shorter)from the timeline 714 of the MAC CE-based CA/BWPconfiguration/reconfiguration. At the end of the CA/BWP configurationtimeline, configuration/reconfiguration should be completed. In someexamples, the CA configuration command and BWP configuration command mayhave different ACK timings and/or configuration timelines.

In one aspect of the disclosure, the UE 602 may report its ACK responsetiming to the base station 604 using, for example, radio resourcecontrol (RRC) signaling or other semi-static methods. For example, afterreceiving a CA/BWP configuration command, the UE 602 may send a messageincluding CA/BWP ACK timing 618 (see FIG. 6; e.g., same slot, next slot,etc.) to the BS 604. In some examples, the UE 602 may include the CA/BWPACK timing in the UE capability information 610. CA/BWP ACK timingindicates the time or slot in which the UE transmits the ACK to a CA/BWPconfiguration command.

A CA configuration command may activate one or more CCs. A CAconfiguration command may deactivate one or more CCs. A BWPconfiguration command may activate a BWP. A BWP configuration commandmay deactivate a BWP. A BWP configuration command may swap BWPs (i.e.,causing the UE to switch from one BWP to another BWP in the same CC ordifferent CCs).

In one aspect of the disclosure, CA/BWP ACK timeline may bepredetermined based on UE capability or category. For example, the BS604 may store information on the timelines for a plurality of UEcapability categories. When the UE 602 reports its UE capabilitycategory, the BS 604 can select the corresponding predetermined timelinefor a CA/BWP configuration command destined to that UE. By determiningand selecting the CA/BWP ACK timeline, the BS 604 may schedule ULresources for the UE to transmit the CA or BWP ACK based on thepredetermined timeline. For example, the UE 602 may be scheduled totransmit the ACK in the same slot in which the UE received the CA/DWPconfiguration command or in a different slot.

In another aspect of the disclosure, the BS 604 may configure the CA/BWPconfiguration/reconfiguration timeline (e.g., timelines 712 and 714)using RRC signaling. The CA/BWP timeline refers to a time period betweenthe activation of the CA/BWP command and the completion ofreconfiguration (e.g., activation/deactivation) of the correspondingCA/BWP. For example, the BS 604 may transmit an RRC message (e.g.,connection reconfiguration 612) including CA/BWP configuration timelineinformation to the UE. In another aspect of the disclosure, the BS 604may transmit the CA/BWP configuration timeline using DCI. For example,the BS 604 may include explicit CA/BWP timeline information in the DCI.In some examples, the CA/BWP configuration timeline may be implied viaACK/NACK timing in the DCI. In that case, CA/BWP should be completedwithin a predetermined period after ACK/NACK. In one example, the CA/BWPconfiguration timeline includes the processing time of CA/BWPconfiguration command (i.e., after which ACK can be sent), RF retuningdelay, total radiated sensitivity (TRS) loop tracking, and channel stateinformation (CSI) report, etc. Therefore, the ACK/NACK timing includedin the DCI allows the UE to decide its end-to-end CA/BWP configurationtimeline.

FIG. 8 is a diagram illustrating a bandwidth part (BWP) adaptationexample according to some aspects of the disclosure. Initially, the UE602 may communicate with the BS 604 using a first BWP (denoted as BWP1in FIG. 8) on a first component carrier (denoted as CC1 in FIG. 8). TheBS 604 may send a BWP configuration command 802 (e.g., BWP adaptation orswitching command) to the UE to switch from the first BWP to a secondBWP (denoted as BWP2 in FIG. 8). In one aspect of the disclosure, the BS604 may send the BWP configuration command 802 using resources of theBWP/CC that undergoes BWP adaptation. In this example, the BS 604transmits the BWP configuration command 802 using resources in BWP1 ofCC1. As a result, the UE 602 switches to use BWP2 of CC1 to communicatewith the BS 604. In one example, BWP1 may be a narrowband BWP, and BWP2may be a wideband BWP having a bandwidth wider than BWP1. In anotherexample, BWP2 may be a narrowband BWP, and BWP1 may be a wideband BWPhaving a bandwidth wider than BWP2. In yet another example, BWP1 andBWP2 may have the same bandwidth but use different frequency bands.

FIG. 9 is a diagram illustrating a second BWP adaptation exampleaccording to some aspects of the disclosure. Initially, the UE 602 maycommunicate with the BS 604 using a first BWP (denoted as BWP1 in FIG.9) on a first CC (denoted as CC1 in FIG. 8). The BS 604 may send a BWPconfiguration command 902 (e.g., BWP adaptation or switching command) tothe UE to switch from the BWP1 to a second BWP (denoted as BWP2 in FIG.9). In one aspect of the disclosure, the BS 604 may send the BWPconfiguration command 902 using resources on a CC2 that is differentfrom CC1 that undergoes BWP adaptation. This example may be referred toas cross-carrier BWP switching. The BS 604 may transmit the BWPconfiguration command 902 using resources in a BWP 904 of CC2. As aresult, the UE 602 switches to use a BWP2 906 of CC1 to communicate withthe BS 604. In one example, BWP1 may be a narrowband BWP, and BWP2 maybe a wideband BWP having a bandwidth wider than BWP1. In anotherexample, BWP2 may be a narrowband BWP, and BWP1 may be a wideband BWPhaving a bandwidth wider than BWP2. In yet another example, BWP1 andBWP2 may have the same bandwidth but use different frequency bands.

FIG. 10 is a diagram illustrating a third BWP adaptation exampleaccording to some aspects of the disclosure. Initially, the UE 602 maycommunicate with the BS 604 using a first BWP 1002 (denoted as BWP1 inFIG. 10) on a first CC (denoted as CC1 in FIG. 10). Then, the BS 604 maytransmit a BWP configuration command 1004 to switch from BWP1 1002 toBWP2 1006. When BWP adaptation is performed on the same CC, the amountof resources (e.g., uplink or UCI resources on a PUCCH) available fortransmitting the corresponding BWP ACK may be different after BWPswitching. In this example, BWP1 and BWP2 are on the same carrier CC1,but BWP2 provides a wider bandwidth. Therefore, the UE 602 may beallocated with more resources for transmitting BWP ACK. In anotherexample, BWP2 may provide a narrower bandwidth. Therefore, the UE 602may have less resources for transmitting BWP ACK after switching.

In one aspect of the disclosure, the UE 602 may transmit the ACK for theBWP configuration command after BWP switching. In this case, the UE mayuse the UCI resources 1008 of BWP2 1006 to transmit the ACK. The BS 604may configure the UCI resources for the ACK based on the availableresources of BWP2 804, in addition to resources for any operations(e.g., ACK for CA activation) based on BWP1 802. A certain interruptionor delay may occur before transmitting the ACK to allow the UE toreconfigure (e.g., retune RF circuitry) to use the new BWP.

In another aspect of the disclosure, the UE 602 may transmit the ACK forthe BWP configuration command before BWP switching. In this case, the UEmay use the UCI resources of BWP1 1002 to transmit the ACK. A certaininterruption or delay may occur after transmitting the ACK to allow theUE to reconfigure (e.g., retune RF circuitry) to use the new BWP2. Insome aspects of the disclosure, the BS 604 may schedule UCI resourcesfor the BWP ACK using RRC or DCI signaling.

FIG. 11 is a flow chart illustrating an exemplary process 1100 forconfiguring CA or BWP in accordance with some aspects of the presentdisclosure. As described below, some or all illustrated features may beomitted in a particular implementation within the scope of the presentdisclosure, and some illustrated features may not be required for theimplementation of all embodiments. In some examples, the process 1100may be carried out by the scheduling entity 400 illustrated in FIG. 4.In some examples, the process 1100 may be carried out by any suitableapparatus or means for carrying out the functions or algorithm describedbelow.

At block 1102, a scheduling entity (e.g., a base station) receives acapability report from a UE. The capability report indicates acapability of the UE to utilize at least one of carrier aggregation (CA)or one or more bandwidth parts. For example, the scheduling entity mayuse a communication circuit 442 (see FIG. 4) and a transceiver 410 toreceive the capability report. In one example, the UE may be any UE(e.g., UE 602) illustrated in any of FIGS. 1, 2, and 6. In someexamples, the capability report may indicate a UE category of the UE.

At block 1104, the scheduling entity may transmit a command to the UE toreconfigure at least one of a CA configuration or a bandwidth part (BWP)configuration. For example, the scheduling entity may use thecommunication circuit 442 and transceiver 410 to transmit the commandThe command may be a CA configuration command or BWP configurationcommand In one example, the scheduling entity may transmit the commandusing DCI. In another example, the scheduling entity may transmit thecommand using MAC CE. The CA configuration command may cause the UE toactivate/deactivate one or more CCs. The BWP configuration command maycause the UE to activate/deactivate BWP.

At block 1106, the scheduling entity may determine an anticipatedresponse timing of an acknowledgment (ACK) of the command (e.g., CAconfiguration command or BWP configuration) based on the capabilityreport received from the UE. The anticipated response timing may be atime delay after which the UE sends an ACK of the command For example,the scheduling entity may use the processing circuit 440 to analyze thecapability report, which may indicate that the UE is capable oftransmitting the ACK after a predetermined time delay in response to thecommand The UE may indicate that it is capable of sending the ACK in thesame slot where the command is received or a different slot. In someexamples, the scheduling entity may determine the ACK timing based onthe UE's category. That is, the scheduling entity may have predeterminedtiming information (e.g., default CA/BWP ACK timing) for various UEcategories.

At block 1108, the scheduling entity may receive the ACK according tothe anticipated response timing. For example, the scheduling entity mayuse the processing circuit 440 to schedule or allocate resources (e.g.,PRBs) for receiving the ACK based on the response timing, and use thecommunication circuit 442 and transceiver 410 to receive the ACK usingthe scheduled resources.

FIG. 12 is a flow chart illustrating an exemplary process 1200 forconfiguring CA or BWP in accordance with some aspects of the presentdisclosure. As described below, some or all illustrated features may beomitted in a particular implementation within the scope of the presentdisclosure, and some illustrated features may not be required forimplementation of all embodiments. In some examples, the process 1200may be carried out by the scheduled entity 500 illustrated in FIG. 5. Insome examples, the process 1200 may be carried out by any suitableapparatus or means for carrying out the functions or algorithm describedbelow.

At block 1202, a scheduled entity (e.g., UE 602) transmits a capabilityreport to a scheduling entity (e.g., base station 604). The capabilityreport indicates a capability of the UE to utilize at least one ofcarrier aggregation (CA) or one or bandwidth parts for wirelesscommunication. The capability report may indicate the UE category of thescheduled entity. For example, the scheduled entity may use acommunication circuit 542 (see FIG. 5) and a transceiver 510 to transmitthe capability report. In one example, the scheduled entity may be a UE(e.g., UE 602) illustrated in any of FIGS. 1, 2, and 6.

At block 1204, the scheduled entity may receive a command from thescheduling entity to reconfigure at least one of a CA configuration or aBWP configuration. For example, the scheduled entity may use thecommunication circuit 542 and transceiver 510 to receive the command Thecommand may be a CA configuration command or BWP configuration commandIn one example, the scheduled entity may receive the command in DCI. Inanother example, the scheduled entity may receive the command in MAC CE.

At block 1206, the scheduled entity may transmit an ACK of the commandusing a timing based on the capability report or UE category. Forexample, the scheduled entity may use the communication circuit 542 andtransceiver 510 to transmit the ACK. The capability report may indicatethat the scheduled entity is capable of transmitting an ACK after apredetermined time delay or in a certain slot after receiving thecommand For example, the scheduled entity may indicate that it iscapable of sending the ACK in the same slot where the command isreceived or a different slot after the slot for receiving the command

In one configuration, the apparatus 400 for wireless communicationincludes means for receiving a capability report from a UE, thecapability report indicating a capability of the UE to utilize at leastone of CA or one or more bandwidth parts. The apparatus 400 furtherincludes means for transmitting a command to the UE to reconfigure atleast one of a CA configuration or a BWP configuration. The apparatus400 further includes means for determining a response timing of an ACKof the command based on the capability report received from the UE. Theapparatus 400 further includes means for receiving the ACK according tothe determined response timing In one aspect, the aforementioned meansmay be the processor 440 and communication circuit 442 in which theinvention resides shown in FIG. 4 configured to perform the functionsrecited by the aforementioned means. In another aspect, theaforementioned means may be a circuit or any apparatus configured toperform the functions recited by the aforementioned means.

In one configuration, the apparatus 500 for wireless communicationincludes means for transmitting a capability report to a schedulingentity (e.g., base station), the capability report indicating acapability of the apparatus 500 (e.g., UE) to utilize at least one of CAor one or more bandwidth parts. The apparatus 500 further includes meansfor receiving a command from the scheduling entity to reconfigure atleast one of a CA configuration or a BWP configuration. The apparatus500 further includes means for transmitting an ACK of the commandaccording to the capability or category of the UE.

Of course, in the above examples, the circuitry included in theprocessor 404/504 is merely provided as an example, and other means forcarrying out the described functions may be included within variousaspects of the present disclosure, including but not limited to theinstructions stored in the computer-readable storage medium 406/506, orany other suitable apparatus or means described in any one of the FIGS.1, 2, and/or 6, and utilizing, for example, the processes and/oralgorithms described herein in relation to FIGS. 6-12.

Several aspects of a wireless communication network have been presentedwith reference to an exemplary implementation. As those skilled in theart will readily appreciate, various aspects described throughout thisdisclosure may be extended to other telecommunication systems, networkarchitectures and communication standards.

By way of example, various aspects may be implemented within othersystems defined by 3GPP, such as Long-Term Evolution (LTE), the EvolvedPacket System (EPS), the Universal Mobile Telecommunication System(UMTS), and/or the Global System for Mobile (GSM). Various aspects mayalso be extended to systems defined by the 3rd Generation PartnershipProject 2 (3GPP2), such as CDMA2000 and/or Evolution-Data Optimized(EV-DO). Other examples may be implemented within systems employing IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB),Bluetooth, and/or other suitable systems. The actual telecommunicationstandard, network architecture, and/or communication standard employedwill depend on the specific application and the overall designconstraints imposed on the system.

Within the present disclosure, the word “exemplary” is used to mean“serving as an example, instance, or illustration.” Any implementationor aspect described herein as “exemplary” is not necessarily to beconstrued as preferred or advantageous over other aspects of thedisclosure. Likewise, the term “aspects” does not require that allaspects of the disclosure include the discussed feature, advantage ormode of operation. The term “coupled” is used herein to refer to thedirect or indirect coupling between two objects. For example, if objectA physically touches object B, and object B touches object C, thenobjects A and C may still be considered coupled to one another—even ifthey do not directly physically touch each other. For instance, a firstobject may be coupled to a second object even though the first object isnever directly physically in contact with the second object. The terms“circuit” and “circuitry” are used broadly, and intended to include bothhardware implementations of electrical devices and conductors that, whenconnected and configured, enable the performance of the functionsdescribed in the present disclosure, without limitation as to the typeof electronic circuits, as well as software implementations ofinformation and instructions that, when executed by a processor, enablethe performance of the functions described in the present disclosure.

One or more of the components, steps, features and/or functionsillustrated in FIGS. 1-12 may be rearranged and/or combined into asingle component, step, feature or function or embodied in severalcomponents, steps, or functions. Additional elements, components, steps,and/or functions may also be added without departing from novel featuresdisclosed herein. The apparatus, devices, and/or components illustratedin FIGS. 1-12 may be configured to perform one or more of the methods,features, or steps described herein. The novel algorithms describedherein may also be efficiently implemented in software and/or embeddedin hardware.

It is to be understood that the specific order or hierarchy of steps inthe methods disclosed is an illustration of exemplary processes. Basedupon design preferences, it is understood that the specific order orhierarchy of steps in the methods may be rearranged. The accompanyingmethod claims present elements of the various steps in a sample order,and are not meant to be limited to the specific order or hierarchypresented unless specifically recited therein.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but are to be accorded the full scope consistentwith the language of the claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. A phrase referring to“at least one of” a list of items refers to any combination of thoseitems, including single members. As an example, “at least one of: a, b,or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, band c. All structural and functional equivalents to the elements of thevarious aspects described throughout this disclosure that are known orlater come to be known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the claims. Moreover, nothing disclosed herein isintended to be dedicated to the public regardless of whether suchdisclosure is explicitly recited in the claims. No claim element is tobe construed under the provisions of 35 U.S.C. § 112(f) unless theelement is expressly recited using the phrase “means for” or, in thecase of a method claim, the element is recited using the phrase “stepfor.”

1. (canceled)
 2. A method of wireless communication at a user equipment(UE), comprising: transmitting a capability report to a schedulingentity, the capability report indicating a capability of the UE toperform a bandwidth part (BWP) reconfiguration in a time period;receiving a command from the scheduling entity, the command indicatingthe BWP reconfiguration; and completing the BWP reconfiguration in thetime period.
 3. The method of claim 2, wherein the receiving the commandcomprises: receiving a BWP configuration command in downlink controlinformation (DCI) of a downlink control channel; receiving a BWPconfiguration command in a medium access control (MAC) control element(CE); or receiving a BWP configuration command in a radio resourcecontrol (RRC) command.
 4. The method of claim 3, wherein the completingthe BWP reconfiguration comprises: reconfiguring a BWP configuration ina first timeline in response to receiving the BWP configuration commandusing the DCI; and reconfiguring the BWP configuration in a secondtimeline in response to receiving the BWP configuration command usingthe MAC CE, and the first timeline is different from the secondtimeline.
 5. The method of claim 2, wherein the command is configured toactivate, deactivate, or switch a BWP used by the UE.
 6. The method ofclaim 2, wherein the receiving the command comprises: receiving a BWPconfiguration command using a first component carrier (CC), wherein theBWP configuration command configures the UE to switch from a first BWPof the first CC to a second BWP of the first CC.
 7. The method of claim2, wherein the receiving the command comprises: receiving a BWPconfiguration command using a first component carrier (CC), wherein theBWP configuration command configures the UE to switch from a first BWPof a second CC to a second BWP of the second CC.
 8. A user equipment(UE) for wireless communication, comprising: a transceiver for wirelesscommunication; a memory; and a processor coupled with the transceiverand the memory, wherein the processor and the memory are configured to:transmit a capability report to a scheduling entity, the capabilityreport indicating a capability of the UE to perform a bandwidth part(BWP) reconfiguration in a time period; receive a command from thescheduling entity, the command indicating the BWP reconfiguration; andcomplete the BWP reconfiguration in the time period.
 9. The UE of claim8, wherein, to receive the command from the scheduling entity, theprocessor and the memory are further configured to: receive a BWPconfiguration command in downlink control information (DCI) of adownlink control channel; receive a BWP configuration command in amedium access control (MAC) control element (CE); or receiving a BWPconfiguration command in a radio resource control (RRC) command.
 10. TheUE of claim 9, wherein, to complete the BWP reconfiguration, theprocessor and the memory are further configured to: reconfigure a BWPconfiguration in a first timeline in response to receiving the BWPconfiguration command using the DCI; and reconfigure the BWPconfiguration in a second timeline in response to receiving the BWPconfiguration command using the MAC CE, and the first timeline isdifferent from the second timeline.
 11. The UE of claim 8, wherein thecommand is configured to activate, deactivate, or switch a BWP used bythe UE.
 12. The UE of claim 8, wherein, to receive the command, theprocessor and the memory are further configured to: receive a BWPconfiguration command using a first component carrier (CC), wherein theBWP configuration command configures the UE to switch from a first BWPof the first CC to a second BWP of the first CC.
 13. The UE of claim 8,wherein, to receive the command, the processor and the memory arefurther configured to: receive a BWP configuration command using a firstcomponent carrier (CC), wherein the BWP configuration command configuresthe UE to switch from a first BWP of a second CC to a second BWP of thesecond CC.
 14. A method of wireless communication at a schedulingentity, comprising: receiving a capability report from a user equipment(UE), the capability report indicating a capability of the UE to performa bandwidth part (BWP) reconfiguration in a time period; andtransmitting a command to the UE, the command indicating the BWPreconfiguration to be completed in the time period.
 15. The method ofclaim 14, wherein the transmitting the command comprises: transmitting aBWP configuration command in downlink control information (DCI) of adownlink control channel; transmitting a BWP configuration command in amedium access control (MAC) control element (CE); or transmitting a BWPconfiguration command in a radio resource control (RRC) command.
 16. Themethod of claim 15, further comprising: receiving a reconfiguringcomplete message in a first timeline corresponding to the BWPconfiguration command transmitted using the DCI; and receiving thereconfiguration complete message in a second timeline corresponding tothe BWP configuration command transmitted using the MAC CE, and thefirst timeline is different from the second timeline.
 17. The method ofclaim 14, wherein the command is configured to activate, deactivate, orswitch a BWP used by the UE.
 18. The method of claim 14, wherein thetransmitting the command comprises: transmitting a BWP configurationcommand using a first component carrier (CC), wherein the BWPconfiguration command configures the UE to switch from a first BWP ofthe first CC to a second BWP of the first CC.
 19. The method of claim14, wherein the transmitting the command comprises: transmitting a BWPconfiguration command using a first component carrier (CC), wherein theBWP configuration command configures the UE to switch from a first BWPof a second CC to a second BWP of the second CC.
 20. A scheduling entityfor wireless communication, comprising: a transceiver for wirelesscommunication; a memory; and a processor coupled with the transceiverand the memory, wherein the processor and the memory are configured to:receive a capability report from a user equipment (UE), the capabilityreport indicating a capability of the UE to perform a bandwidth part(BWP) reconfiguration in a time period; and transmit a command to theUE, the command indicating the BWP reconfiguration to be completed inthe time period.
 21. The scheduling entity of claim 20, wherein, totransmit the command to the UE, the processor and the memory are furtherconfigured to: transmit a BWP configuration command in downlink controlinformation (DCI) of a downlink control channel; transmit a BWPconfiguration command in a medium access control (MAC) control element(CE); or transmit a BWP configuration command in a radio resourcecontrol (RRC) command.
 22. The scheduling entity of claim 21, whereinthe processor and the memory are further configured to: receive areconfiguration complete message in a first timeline corresponding tothe BWP configuration command transmitted using the DCI; and receive thereconfiguration complete message in a second timeline corresponding tothe BWP configuration command transmitting using the MAC CE, and thefirst timeline is different from the second timeline.
 23. The schedulingentity of claim 20, wherein the command is configured to activate,deactivate, or switch a BWP used by the UE.
 24. The scheduling entity ofclaim 20, wherein, to transmit the command, the processor and the memoryare further configured to: transmit a BWP configuration command using afirst component carrier (CC), wherein the BWP configuration commandconfigures the UE to switch from a first BWP of the first CC to a secondBWP of the first CC.
 25. The scheduling entity of claim 20, wherein, totransmit the command, the processor and the memory are furtherconfigured to: transmit a BWP configuration command using a firstcomponent carrier (CC), wherein the BWP configuration command configuresthe UE to switch from a first BWP of a second CC to a second BWP of thesecond CC.